feat(create-expert): Generate Expert Ecosystems with Usability Focus#348
feat(create-expert): Generate Expert Ecosystems with Usability Focus#348
Conversation
Transform create-expert from generating single experts to generating expert ecosystems (main + demo + setup + doctor). - Add usability properties to property-extractor - Rename expert-builder to ecosystem-builder - Add usability-manager for PDCA on usability - Update expert-tester with usability stage - Update report-generator for ecosystems Closes #337 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
![cursor[bot]](https://avatars.githubusercontent.com/in/1210556?s=60&v=4){kind=small}
| - If demo missing/broken: Fix demo expert instructions | ||
| - If setup broken: Fix setup automation flow | ||
| - If errors unclear: Add actionable "To fix:" guidance | ||
| - If doctor missing: Generate doctor expert |
There was a problem hiding this comment.
Usability manager may incorrectly create doctor expert
The USABILITY_MANAGER_INSTRUCTION's Act phase says "If doctor missing: Generate doctor expert" without any conditional check. However, ECOSYSTEM_BUILDER_INSTRUCTION explicitly states doctor experts are only created "IF external dependencies exist". This inconsistency means usability-manager could create a doctor expert even when there are no external dependencies, contradicting the ecosystem design where doctor experts are only meant for experts with external API keys or services.
Additional Locations (1)
|
|
||
| [experts."expert-name".skills."@perstack/base"] | ||
| ### 4. Confirm Success | ||
| Output: "✓ Setup complete! Try: npx perstack run <name> \\"your query\\"" |
There was a problem hiding this comment.
Incorrect escaping produces visible backslashes in output template
The escaped double quotes \\"your query\\" in the Setup Expert Template instruction are unnecessary in JavaScript template literals. This produces the literal characters \"your query\" with visible backslashes in the final TOML instruction. When the generated setup expert displays the success message, it would show something like npx perstack run name \"your query\" with visible backslash characters instead of clean quotes, which looks incorrect to end users.
1 participant
Summary
Transform
create-expertfrom generating single experts to generating expert ecosystems with built-in usability:<name>-demo): Works immediately with sample data (no setup required)<name>-setup): Automated configuration wizard (only if external deps exist)<name>-doctor): Troubleshooting assistant (only if external deps exist)Changes
Expected Behavior
After this change, when a user creates an expert with external dependencies:
npx create-expert --headless --description "A web researcher using Brave Search"They get an ecosystem:
Test Plan
Closes #337
🤖 Generated with Claude Code
Note
Transforms
create-expertto produce an expert ecosystem instead of a single expert.expert-builderwithecosystem-builder; adds templates formain,-demo,-setup,-doctor; append-only edits toperstack.tomlproperty-extractornow returns usability properties (Zero-Config, Setup-Automation, Error-Guidance) and external dependenciesusability-manager; updatesexpert-testerwith a "usability" stage to validate demo w/o setup, guided setup, doctor diagnostics, and actionable error guidancereport-generatorupdated for ecosystem-aware outputs and quick start commandscreate-expertdelegates to includeecosystem-builderandusability-manager; adds/renames expert definitions in TOMLWritten by Cursor Bugbot for commit 8487774. This will update automatically on new commits. Configure here.